Some questions about frontend development that might be in your next job interview. The questions were formulated by @mauvieira, a super senior fullstack developer

• What are the strategies we can use to optimize the performance of web applications?

  • CDNs, GraphQL (maybe) to reduce overfetching, improve backend performance, use SSR and/or SSG, lazy loading for loading assets only when it's needed, minimize and compress HTML, CSS and JS files, and optimize images by compressing and resizing them.

• What are Web Vitals (LCP, FID, CLS)? And how are they applied in the real world?

A pattern for building personal knowledge bases using LLMs. Extended with lessons from building agentmemory 10K Stars ⭐️, a persistent memory engine for AI coding agents.

This builds on Andrej Karpathy's original LLM Wiki idea file. Everything in the original still applies. This document adds what we learned running the pattern in production: what breaks at scale, what's missing, and what separates a wiki that stays useful from one that rots.

Currently, Working on AKBP: Agent Knowledge Base Protocol based on my findings, a protocol for creating, updating, retrieving, and sharing durable knowledge across AI agents.

(00:00:00) – How batch size affects token cost and speed
(00:32:09) – How MoE models are laid out across a GPU racks
(00:47:12) – How pipeline parallelism moves model layers across racks
(01:03:37) – Why Ilya said, “As we now know, pipelining is not wise.”
(01:18:59) – Because of RL, models may be 100x over-trained beyond Chinchilla-optimal
(01:33:02) – Deducing long context memory costs from API pricing
(02:04:02) – Convergent evolution between neural nets and cryptography

Export all your ChatGPT conversations as JSON + Markdown + HTML + ZIP. Works with ChatGPT Business/Team/Enterprise accounts (including SSO/Okta).

• JSON — Raw conversation data from the API
• Markdown — Clean text with headers per message, relative links to downloaded files
• HTML — ChatGPT-style conversation viewer with sidebar navigation, syntax-highlighted code blocks, and embedded images

Use this as a baseline across all Macs to reduce exposure to fast-moving supply-chain attacks, where a malicious package version is published, installed by early updaters, then removed hours later.

The default policy I would use is:

• Personal/dev machines: 3 days.
• CI and production lock refresh jobs: 3 to 7 days.
• Emergency security fixes: bypass deliberately, one package at a time, with a reviewed lockfile diff.

Inspiration: Deis Commit Style Guide

I often quote Deis in sections below.

It makes going back and reading commits easier. It also allows you to spend less time thinking about what your commit message should be.

You have a repository, call it alice/repo. You would like to transfer it to the user bob, so it will become bob/repo.

However, you make heavy use of the GitHub Pages feature, so that people are often accessing https://alice.github.io/repo/. GitHub will helpfully redirect all of your repository stuff hosted on github.com after the move, but will not redirect the GitHub Pages hosted on github.io.